Tim Dawson (20/08/2012)
What you see is correct. The correct way of reporting an EET at an FIR boundary is the EET/LFRR0123 format. To use the name of an airways reporting point there, or a lat/lon, would be an error.
I do not know what MN1 and MN2 are, but they have no place in a flightplan. The only things that should make up a flightplan route are airways reporting points, radio navaids or lat/lons.Hi Tim, you may be right in that the generated flightplan is syntactically correct. However, I can only confirm the experience of my fellow fliers that a flightplan like the one generated by SD would raise eyebrows with ATC and make them come back and ask me questions. Those border crossing points such as, e.g., GOLVA are specifically for reporting a border crossing and use in flight plans.
MN1 and MN2 are waypoints associated with the airport LJMB and expected to be used when landing at LJMB. They are part of my route and hence also part of the Route description in the flight plan. They do bear some significance because the approach controller at LJMB immediately knows that I will follow a sensible route. If I don't put these in the flight plan I will get them as part of the entry clearance in his airspace.
Either way is OK, but there is a reason that I file them as part of my routing. And if I use them as part of my SD route they show up in the fllightplan anyway. So if they already show up it is very confusing not to have them show up with their names.
Somthing to consider...
Thanks very much for a great product and cheers, -- Chris.